Systems and methods for image data management

ABSTRACT

A system and method for image data management. A tiled representation of a data set is accessed. The tiled representation includes a plurality of high-resolution tiles and a plurality of reduced-resolution tiles. A request to access said data set from a computing device is received. An image display window is determined based on said request from the computing device, where the image display window corresponds to a displayable image for display on the display device. At least one overlapping image to send the computing device is determined based on said image display window, where the at least one overlapping image is selected from the scaled full images, the plurality of high-resolution tiles, and the plurality of reduced resolution tiles. At least a portion of the at least one overlapping image is sent to the computing device.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 13/354,627, filed on Jan. 20, 2012, specification of which isherein incorporated by reference in its entirety.

BACKGROUND OF THE INVENTION

1. Field of the Invention

Embodiments of the invention described herein pertain to the field ofcomputer systems. More particularly, but not by way of limitation, oneor more embodiments of the invention enable systems and methods forimage data management.

2. Description of the Related Art

Access to high-resolution image data is useful in a wide variety ofapplications. In almost any field, high-resolution image data isdesirable over lower resolution images. Image size and/or imageresolution are often reduced to provide quicker access or to facilitateaccess to mobile devices with limited resources. Often, high-resolutionimage data can enhance user experience.

In some applications, access to high-resolution image data is necessary.For example, although providing quick access to lower resolution medicalimaging data may be useful, full resolution medical imaging data must beconsulted before making a final diagnosis. Other importanthigh-resolution image data that may also be important include mapping,schematics, geographical data, advertising, publishing, design,professional photography, and other types of image data.

Often, high-resolution image data involves private, confidential orsensitive information that cannot be made publicly available fordownload. In these instances, it is standard to store high-resolutionimage data on a secure, centralized server. Access to thehigh-resolution image data may be granted to authorized users throughstandard security protocols.

It is desirable to provide high-resolution image data to computingdevices, even when the computing devices have limited computingresources. Limited computing resources may include processing power,graphical processing power, memory, network bandwidth, and any othercomputing resource. At the same time, there is a demand for access tohigh-resolution image data at near real-time speed. In one instance, theresolution of the file may be reduced to provide quicker access at theexpense of image resolution. In another instance, the high-resolutionimage data file may be downloaded before a user may view and navigatethe image file. However, the delay involved in downloading larger imagedata files makes this method less useful, especially if collaboration isdesired.

In a typical collaboration scenario, one specialist may seek the adviceor opinion of another specialist regarding the high-resolution imagedata. However, existing solutions do not providing the second specialistquick access to the high-resolution image data at near real-time speed.

To overcome the problems and limitations described above, there is aneed for systems and methods for image data management.

BRIEF SUMMARY OF THE INVENTION

Systems and methods for image data management described herein providehigh-resolution image data at near real-time speed by preprocessing thehigh-resolution image files into tiles of varying resolution. A clientdevice requests image data based on user navigation within the imagefile. Depending on an image display window, a subset of tiles at thedesired resolution is sent to the client device, resulting in access tothe high-resolution image data at near real-time speed.

One or more embodiments of the system and method for image datamanagement described herein enable a computer-readable medium includingcomputer-readable instructions for providing image data. Execution ofthe computer-readable instructions by one or more processors causes theone or more processors to carry out steps.

One of the steps carried out by the one or more processors is accessinga tiled representation of a data set including image data athigh-resolution. The tiled representation may include a plurality ofhigh-resolution tiles, where none of the plurality of high resolutiontiles is larger than a maximum tile size. The tiled representation mayfurther include a plurality of reduced-resolution tiles, where none ofthe plurality of reduced resolution tiles is larger than the maximumtile size.

Another step carried out by the one or more processors is receiving arequest to access the data set from a computing device. The computingdevice is communicatively coupled with a display device.

Another step carried out by the one or more processors is determining animage display window based on the request from the computing device. Theimage display window corresponds to a displayable image for display onthe display device.

Another step carried out by the one or more processors is determining atleast one overlapping image to send the computing device based on theimage display window. The at least one overlapping image is selectedfrom the plurality of high-resolution tiles and the plurality of reducedresolution tiles.

Another step carried out by the one or more processors is sending atleast a portion of the at least one overlapping image to the computingdevice for display in real time.

In one or more embodiments, the steps may further include obtaining adata set including image data at high-resolution, generating a pluralityof scaled full images at a plurality of resolutions that includes a fullresolution image and at least one reduced resolution image, generating aplurality of high-resolution tiles based on the full resolution image,where none of the plurality of high resolution tiles is larger than amaximum tile size, and generating a plurality of reduced-resolutiontiles based on the at least one reduced resolution image, where none ofthe plurality of reduced resolution tiles is larger than the maximumtile size; and storing the tiled representation of the data set.

For example, the maximum file size is based on a GPU limit. The maximumtile size may be 1024 pixels by 1024 pixels. The image data may includea plurality of pixels including 16 bits per pixel.

In one or more embodiments, the plurality of reduced resolutions includeresolutions of (½, . . . ½^(n)), where n is an integer greater than orequal to 1.

In one or more embodiments, the at least one overlapping image includesa plurality of tiles at a new resolution, where the new resolution isthe next higher resolution generated compared to the resolutioncurrently displayed on the display device.

In one or more embodiments, the steps further include receiving arequest from the computing device to access data corresponding to anupdated image display window, determining at least one updated image tosend the computing device based on the updated image display window,where the at least one updated image is selected from the plurality ofhigh-resolution tiles and the plurality of reduced resolution tiles, andsending the at least one updated image to the computing device fordisplay in real time.

The image data may include full-resolution medical imaging data. Forexample, the data set may comply with the Digital Imaging andCommunications in Medicine (DICOM) file format definition. The imagedata may include video data.

In one or more embodiments, the steps further include providing metadataassociated with the data set to the computing device.

The steps may also include receiving new metadata from the computingdevice, and associating the new metadata with the data set.

The steps may also include sending the computing device background dataincluding unsent image data selected from the plurality ofhigh-resolution tiles and the plurality of reduced-resolution tiles.

One or more embodiments of the system and method for image datamanagement described herein enable a computer-readable medium includingcomputer-readable instructions for displaying image data, whereexecution of the computer-readable instructions by one or moreprocessors causes the one or more processors to carry out steps.

One of the steps carried out by the one or more processors is sending arequest to access medical imaging data from a server.

Another step carried out by the one or more processors is receiving aninitial image. In one or more embodiments, the initial image is a scaledfull image of the medical imaging data, where the reduced resolutionimage is limited in size based on a GPU limit.

Another step carried out by the one or more processors is processing theinitial image on a graphical processor unit (GPU).

Another step carried out by the one or more processors is displaying adisplayed image based on initial image on a display device.

Another step carried out by the one or more processors is receiving aplurality of overlap images from the server, where a resolution of theplurality of overlap images is higher than a resolution of the scaledfull image, and where the plurality of overlap images is limited insize.

Another step carried out by the one or more processors is processing theplurality of overlap images in series on the GPU to update at least aportion of the displayed image with at least a portion of an overlapimage.

Another step carried out by the one or more processors is acceptinginput from a user including a change in a view of the medical imagingdata.

Another step carried out by the one or more processors is sending arequest including the change in the view to the server.

Another step carried out by the one or more processors is receiving atleast one additional image from the server, where the at least oneadditional image is limited in size.

Another step carried out by the one or more processors is processing theat least one additional image in series on the GPU to update at least aportion of the displayed image with at least a portion of an overlapimage, where the portion of the overlap image is determined based on thechange in the view.

In one or more embodiments, the plurality of overlap images and the atleast one additional image are limited in size based on a GPU limit. Theplurality of overlap images may be limited in size based on a GPU limit.The plurality of overlap images may be limited in size to 1024 pixels by1024 pixels at 16-bits per pixel.

In one or more embodiments, the medical imaging data complies with theDigital Imaging and Communications in Medicine (DICOM) file formatdefinition. The medical imaging data may include video data.

The steps may also include receiving and displaying metadata associatedwith a portion of the medical imaging data associated with the displayedimage.

In one or more embodiments, the steps further include accepting newmetadata from the user, and sending the new metadata to the serve. Thesteps may also include storing at least one of the plurality of overlapimages and the at least one additional image in a local memory store,and processing at least one stored image on the GPU to update at least aportion of the displayed image based on the change in the view.

The steps may also include receiving background data including unsentimage data selected from the image data, the plurality ofhigh-resolution tiles, and the plurality of reduced-resolution tiles.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other aspects, features and advantages of the inventionwill be more apparent from the following more particular descriptionthereof, presented in conjunction with the following drawings wherein:

FIG. 1 illustrates a general-purpose computer and peripherals that whenprogrammed as described herein may operate as a specially programmedcomputer in accordance with one or more embodiments of systems andmethods for image data management.

FIG. 2 illustrates an exemplary image data management system inaccordance with one or more embodiments of systems and methods for imagedata management.

FIG. 3A illustrates exemplary scaled full images in accordance with oneor more embodiments of systems and methods for image data management.

FIG. 3B illustrates exemplary high-resolution tiles andreduced-resolution tiles in accordance with one or more embodiments ofsystems and methods for image data management.

FIG. 4 illustrates exemplary image display windows in accordance withone or more embodiments of systems and methods for image datamanagement.

FIG. 5 illustrates exemplary image display windows in accordance withone or more embodiments of systems and methods for image datamanagement.

FIG. 6 illustrates an exemplary use of windowing in accordance with oneor more embodiments of systems and methods for image data management.

FIG. 7 is a flowchart for an exemplary method for processing image datain accordance with one or more embodiments of systems and methods forimage data management.

FIG. 8 is a flowchart for an exemplary method for providing image datain accordance with one or more embodiments of systems and methods forimage data management.

FIG. 9 is a flowchart for an exemplary method for providing image datain accordance with one or more embodiments of systems and methods forimage data management.

FIG. 10 is a flowchart for an exemplary method for displaying image datain accordance with one or more embodiments of systems and methods forimage data management.

FIG. 11 is a flowchart for an exemplary method for displaying medicalimaging data in accordance with one or more embodiments of systems andmethods for image data management.

FIG. 12 is a flowchart for an exemplary method for image datacollaboration in accordance with one or more embodiments of systems andmethods for image data management.

FIG. 13 illustrates an exemplary collaborative image data managementsystem in accordance with one or more embodiments of systems and methodsfor image data management.

DETAILED DESCRIPTION

Systems and methods for the image data management will now be described.In the following exemplary description numerous specific details are setforth in order to provide a more thorough understanding of embodimentsof the invention. It will be apparent, however, to an artisan ofordinary skill that the present invention may be practiced withoutincorporating all aspects of the specific details described herein.Furthermore, although steps or processes are set forth in an exemplaryorder to provide an understanding of one or more systems and methods,the exemplary order is not meant to be limiting. One of ordinary kill inthe art would recognize that the steps or processes may be performed ina different order, and that one or more steps or processes may beperformed simultaneously or in multiple process flows without departingfrom the spirit or the scope of the invention. In other instances,specific features, quantities, or measurements well known to those ofordinary skill in the art have not been described in detail so as not toobscure the invention. Readers should note that although examples of theinvention are set forth herein, the claims, and the full scope of anyequivalents, are what define the metes and bounds of the invention.

FIG. 1 illustrates a general-purpose computer and peripherals that whenprogrammed as described herein may operate as a specially programmedcomputer in accordance with one or more embodiments of systems andmethods for image data management.

At least one processor 107 may be coupled to bi-directionalcommunication infrastructure 102 such as communication infrastructuresystem bus 102. Communication infrastructure 102 may generally be asystem bus that provides an interface to the other components in thegeneral-purpose computer system such as processor 107, main memory 106,display interface 108, secondary memory 112 and/or communicationinterface 124.

The at least one processor may include at least one graphics processingunit (GPU). As used herein, the term GPU refers to any specializedcircuit design to accelerate image processing in a frame buffer foroutput. A GPU may be present on a video card, a motherboard, or as acomponent of a CPU.

Main memory 106 may provide a computer readable medium for accessing andexecuted stored data and applications. Display interface 108 maycommunicate with display unit 110 that may be utilized to displayoutputs to the user of the specially-programmed computer system. Displayunit 110 may comprise one or more monitors that may visually depictaspects of the computer program to the user. Main memory 106 and displayinterface 108 may be coupled to communication infrastructure 102, whichmay serve as the interface point to secondary memory 112 andcommunication interface 124. Secondary memory 112 may provide additionalmemory resources beyond main memory 106, and may generally function as astorage location for computer programs to be executed by processor 107.Either fixed or removable computer-readable media may serve as Secondarymemory 112. Secondary memory 112 may comprise, for example, hard disk114 and removable storage drive 116 that may have an associatedremovable storage unit 118. There may be multiple sources of secondarymemory 112 and systems implementing the solutions described in thisdisclosure may be configured as needed to support the data storagerequirements of the user and the methods described herein. Secondarymemory 112 may also comprise interface 120 that serves as an interfacepoint to additional storage such as removable storage unit 122. Numeroustypes of data storage devices may serve as repositories for datautilized by the specially programmed computer system. For example,magnetic, optical or magnetic-optical storage systems, or any otheravailable mass storage technology that provides a repository for digitalinformation may be used.

Communication interface 124 may be coupled to communicationinfrastructure 102 and may serve as a conduit for data destined for orreceived from communication path 126. A network interface card (NIC) isan example of the type of device that once coupled to communicationinfrastructure 102 may provide a mechanism for transporting data tocommunication path 126. Computer networks such Local Area Networks(LAN), Wide Area Networks (WAN), Wireless networks, optical networks,distributed networks, the Internet or any combination thereof are someexamples of the type of communication paths that may be utilized by thespecially program computer system. Communication path 126 may compriseany type of telecommunication network or interconnection fabric that cantransport data to and from communication interface 124.

To facilitate user interaction with the specially programmed computersystem, one or more human interface devices (HID) 130 may be provided.Some examples of HIDs that enable users to input commands or data to thespecially programmed computer may comprise a keyboard, mouse, touchscreen devices, microphones or other audio interface devices, motionsensors or the like, as well as any other device able to accept any kindof human input and in turn communicate that input to processor 107 totrigger one or more responses from the specially programmed computer arewithin the scope of the system disclosed herein.

While FIG. 1 depicts a physical device, the scope of the system may alsoencompass a virtual device, virtual machine or simulator embodied in oneor more computer programs executing on a computer or computer system andacting or providing a computer system environment compatible with themethods and processes of this disclosure. In one or more embodiments,the system may also encompass a cloud computing system or any othersystem where shared resources, such as hardware, applications, data, orany other resource are made available on demand over the Internet or anyother network. In one or more embodiments, the system may also encompassparallel systems, multi-processor systems, multi-core processors, and/orany combination thereof. Where a virtual machine, process, device orotherwise performs substantially similarly to that of a physicalcomputer system, such a virtual platform will also fall within the scopeof disclosure provided herein, notwithstanding the description herein ofa physical system such as that in FIG. 1.

FIG. 2 illustrates an exemplary image data management system inaccordance with one or more embodiments of systems and methods for imagedata management.

System 200 includes image data management system 202. Image datamanagement system 202 includes software and hardware resources forimplementing systems and methods for image data management describedherein.

Image data management system 202 includes image data store 204. Imagedata store 204 is configured to store one or more tiled representationof a data set that includes image data at high resolution. The tiledrepresentation includes a plurality of high-resolution tiles and aplurality of reduced resolution tiles. None of the high-resolution tilesand reduced resolution tiles is larger than the maximum tile size. Themaximum tile size may be based on an image size or a file size. In oneor more embodiments, the maximum tile size is based on a GPU limitation.

The image data may include video data. In one or more embodiments, thedata set includes full resolution medical imaging data. The medicalimaging data may include any medical imaging data that complies with theDigital Imaging and Communications in Medicine (DICOM) file formatdefinition. DICOM is a standard for handling, storing, printing andtransmitting information in medical imaging. Medical imaging data thatmay be stored in a DICOM data set includes x-ray, angiogram, MRI, CT,ultrasound, nuclear, and any other type of medical imaging datacompatible with the DICOM standard.

Image data management system 202 further includes data streaming module206. Data streaming module 206 is configured to deliver at least aportion of a tiled representation stored in image data store 204 to oneor more client devices 220-224. Data streaming module 206 may beconfigured to provide data to one or more client devices 220-204 basedon a request from a client device.

Image data management system 202 optionally includes collaborationmodule 208. Collaboration module 208 is configured to manage one or morecollaboration sessions between a plurality of client devices 220-224. Anexemplary collaboration session illustrated in FIG. 13.

Although the elements of image data management system 202 (e.g. imagedata store 204, data streaming module 206 and collaboration module 208)are shown as distinct modules for purposes of illustration, one ofordinary skill in the art would recognize that these elements of imagedata management system 202 may be implemented in an integrated mannerwithout departing from the spirit or the scope of the invention.

System 200 further includes one or more client devices 220-224. Clientdevices 220-224 may include any computing device, including anygeneral-purpose computer and/or any mobile computing device. Forexample, client devices to 220-224 may include a desktop computer, alaptop computer, a mobile tablet device, a PDA, a mobile telephone, asmart phone, or any other device capable of implementing the systems andmethods for image data management described herein. In one or moreembodiments, client devices 220-224 include one or more network-enabledmobile computing devices with a GPU.

Client devices 220-224 are configured to implement client system 230.Client system 230 includes software and hardware resources forimplementing systems and methods for image data management describedherein.

Client system 230 includes device data store 232. Device data store 232is configured to store data corresponding to one or more tiledrepresentations of a data set that includes image data athigh-resolution. Device data store 232 may also store metadatacorresponding to one or more tiled representations. In one or moreembodiments, device data store 232 resides in a secondary memory of aclient device. A total size limit of device data store 232 may beimposed by device application 234 and/or an external limit to clientsystem 230, such as an operating system limit of client device 224.

Client system 230 further includes device application 234. Deviceapplication 234 may include computer-readable instructions stored on atangible computer-readable medium of a client device.

Device application 234 includes data manager 236. Data manager 236 isconfigured to communicate with image data system 202 to request andreceive at least a portion of a tiled representation of a data set thatincludes image data at high-resolution. The tiled representationincludes a plurality of high-resolution tiles and a plurality of reducedresolution tiles. The tiled representation may include full-resolutiontiles and reduced-resolution tiles at the original bit depth of thehigh-resolution image data. None of the high-resolution tiles andreduced resolution tiles is larger than the maximum tile size. Themaximum tile size may be based on an image size or a file size. In oneor more embodiments, the maximum tile size is based on a GPU limitation.

The image data may include video data. In one or more embodiments, thedata set includes full resolution medical imaging data. The medicalimaging data may include any medical imaging data that complies with theDICOM file format definition.

Data manager 236 may be configured to process at least a portion ofmultiple tiled representations, each tiled representation correspondingto a different data set. In one or more embodiments, data manager 236 isconfigured to store at least a portion of one or more DICOM files. Datamanager 236 may also be configured to process metadata associated with atiled representation.

Data manager 236 may store data corresponding to one or more tiledrepresentations in device data store 232. In one or more embodiments,data manager 236 is configured to manage the storage of data in devicedata store 232. Data manager 236 may manage the storage of data takinginto consideration a total size limit of device data store, includingany size limit imposed by device application 234 or a size limitexternal to client system 230.

Device application 234 further includes display manager 238. Displaymanager 238 is configured to manage the display of data received fromimage data management system 202 and/or image data stored in device datastore 232. Display manager 238 constructs a final image for display on adisplay device of the client device. In one or more embodiments, displaymanager 238 interacts with a GPU of the client device to display orupdate either the entire displayed image or one or more portions of thedisplayed image. Display manager 238 may be configured to modify one ortiles to reduce a bit depth of the tile based on a GPU limitation.

The displayed image corresponds to an image display window. The imagedisplay window is used to determine the appropriate portion of the dataset to currently display. Device application 234 may access user inputreceived from a user interface provided to a user of the client deviceto determine the current image display window. In one or moreembodiments, display manager 238 manages, constructs and/or updates thefinal image for display based on the image display window.

Optionally, device application 234 further includes collaborationmanager 240. Collaboration manager 240 is configured to manage one ormore collaboration sessions between a plurality of client devices. Anexemplary collaboration session illustrated in FIG. 13.

Although the elements of client system 230 (e.g. device data store 230,device application 234, data manager 236, display manager 238 andcollaboration manager 240) are shown as distinct modules for purposes ofillustration, one of ordinary skill in the art would recognize thatthese elements of client system 230 may be implemented in an integratedmanner without departing from the spirit or the scope of the invention.

System 200 further includes network 250. Image data management system202 communicates with client devices 220-224 over network 250. Network250 may include one or more Local Area Networks (LAN), Wide AreaNetworks (WAN), wireless networks, cellular data networks, opticalnetworks, distributed networks, the Internet, or any combinationthereof.

FIG. 3A illustrates exemplary scaled full images in accordance with oneor more embodiments of systems and methods for image data management.Scaled full images 300 include full resolution image 302. Fullresolution image 302 is a full representation of high-resolution imagedata. Full resolution image 302 has the highest resolution of scaledfull images 300. In one or more embodiments, full resolution image 302may have the same resolution as the high-resolution image data, enablingimage data to be provided at the original resolution in accordance withone or more systems and methods for image data management.Alternatively, full resolution image 302 may have a lower resolution maybe used compared to the original image data, as long as full resolutionimage 302 has a higher resolution output of scaled full images 300. Inthis case, full resolution image 302 has a maximum resolution that oneor more systems and methods for image data management is configured toprovide.

Scaled full images 300 further include at least one reduced resolutionimage 304-306. Reduced resolution images 304-306 are fullrepresentations of high-resolution image data. Reduced resolution images304-306 have a lower resolution relative to full resolution image 302.In one or more embodiments, the lowest resolution image 306 is limitedin size based on a GPU limitation. The at least one reducedrepresentation 304-306 may included resolutions of 1/m, 1/(m²), . . .1/m^(n), where n is an integer greater than or equal to 1 and where m isa real number greater than 1. The at least one reduced representation304-306 may include resolutions of ½ . . . ½^(n), where n is an integergreater than or equal to 1.

In one or more embodiments, scaled full images 300 include a pluralityof images that represent video data. As used herein, the term “image”includes any graphical representation, including any multi-framedgraphical representation as well as any single-frame graphicalrepresentation. In one or more embodiments, scaled full images 300represent medical imaging data. The medical imaging data may include anymedical imaging data that complies with the DICOM file formatdefinition.

FIG. 3B illustrates exemplary high-resolution tiles andreduced-resolution tiles in accordance with one or more embodiments ofsystems and methods for image data management.

Tiled representation 320 is a tiled representation of high-resolutionimage data. Tiled representation 320 includes high-resolution tiles 335and reduced-resolution tiles 345, 355 and 362. Together, individualhigh-resolution tiles 335 form a full representation 330 ofhigh-resolution image data. In one or more embodiments, fullrepresentation 330 may have the same resolution as the high-resolutionimage data. Alternatively, full representation 330 may have a lowerresolution may be used compared to the original high-resolution imagedata, but a higher resolution then reduced representations 340, 350 and360. In one or more embodiments, individual full resolution tiles 335are generated based on a full resolution image, such as full resolutionimage 302. Full-resolution tiles 335 may include tiles at the originalbit depth of the high-resolution image data.

Reduced resolution tiles 345, 355 and 362 correspond to at least onereduced representation 340, 350 and 360. In one or more embodiments,individual reduced resolution tiles 345, 355 and 362 are generated basedon at least one reduced resolution image, such as reduced resolutionimages 304-306. Reduced resolution tiles 345, 355 and 362 may includetiles at the original bit depth of the high-resolution image data.

The at least one reduced representation 340, 350 and 360 may includeresolutions of ½ . . . ½^(n), where n is an integer greater than orequal to 1. In one or more embodiments, reduced-resolution tiles aregenerated for reduced representations 340, 350 and 360 such that thesmallest reduced representation 360 is made up of a single tile 362.

In one or more embodiments, none of the high-resolution tiles and/or thereduced-resolution tiles is larger than a maximum tile size. The maximumtile size may be based on an image size or a file size. In one or moreembodiments, the maximum tile size is based on a GPU limitation,including a memory limitation, an image size limitation, or any otherGPU limitation, including limitations imposed on GPU processing that areexternal to the GPU. In one or more embodiments, the maximum tile sizefor a 2D image is 1024×1024. Alternatively, a maximum tile size for a 2Dimage may be set at 2048×2048, or any other limit based on a GPUlimitation. The maximum file size may also be set by a memory size. Forexample, in one or more embodiments, the maximum file size is about 5MB. Alternatively, the tile may exceed a GPU limitation when a tile isat a current bit depth, but may meet a GPU limitation when the bit depthis reduced.

High-resolution tiles 335 and/or reduced-resolution tiles 345, 355 and362 may include one or more border tiles 362-372. Border tiles 362-372represent tiles containing less information than the maximum tile size.One of ordinary skill in the art will recognize that any method suitablefor handling partial tiling may be used without departing from thespirit or the scope of the invention.

FIG. 4 illustrates exemplary image display windows in accordance withone or more embodiments of systems and methods for image datamanagement. A plurality of tiles 400 is illustrated with exemplary imagedisplay windows superimposed. Tiles 400 are arranged to form arepresentation of high-resolution image data at a set resolution. Imagedisplay window 410 and 430 correspond to a viewable area to be displayedon a display device of a client device. The client device is configuredto allow a user to move the viewable area to be displayed on the displaydevice. In one or more embodiments, the client device is configured tochange an orientation of the viewable area to be displayed on thedisplay device. For at least these reasons, image display windows410-430 may change position and/or orientation with respect to tiles400.

For example, image display window 410 corresponds to a viewable area ina portrait orientation. A displayable image corresponding to imagedisplay window 410 is constructed from a subset of the plurality oftiles 412-422. The subset of the plurality of tiles, or overlap images412-422, overlap with image display window 410 when tiles 400 arearranged to form the representation of the high-resolution image data.

The displayable image may be constructed by either a server of the imagedata management system or the client device. In one or more embodiments,the displayable image is constructed by a GPU of the client device byindividually processing overlapping images 412-422, where overlap images412-422 are limited in size based on a GPU limitation. In one or moreembodiments, overlap images 412-422 may exceed a GPU limitation at acurrent bit depth; processing the overlap images 412 to reduce a bitdepth may bring the overlap images 412-422 within the GPU limitation.The bit depth may be selectively reduced to retain a specific subset ofinformation present in the original overlap image. The GPU limitationmay include a memory limitation, an image size limitation, or any otherGPU limitation, including limitations imposed on GPU processing that areexternal to the GPU. For example, the GPU may be configured to processoverlap images 412-422 in series, updating at least a portion of thedisplayable image with at least a portion of each overlap image as it isprocessed.

Image display window 430 corresponds to a viewable area in a landscapeorientation. A display image corresponding to image display window 430is constructed from a subset of the plurality of tiles 432-438. Thesubset of the plurality of tiles, or overlap images 432-438, overlapwith image display window 430 when tiles 400 are arranged to form therepresentation of the high-resolution image data.

FIG. 5 illustrates exemplary image display windows in accordance withone or more embodiments of systems and methods for image datamanagement. A plurality of tiles 500 is illustrated with exemplary imagedisplay windows superimposed. Tiles 500 are arranged to form arepresentation of high-resolution image data at a set resolution.

In one or more embodiments, the user of the client device may change aresolution of the displayable image. When the resolution changessignificantly, tiles of a different resolution may be provided. A usermay be allowed to change a resolution of the displayable image to aresolution other than a resolution of a high-resolution tile or anyreduced resolution tiles. In this case, upscaling or downscalingoperations may be performed. In one or more embodiments, upscaling ordownscaling operations are performed on a client device. One of ordinaryskill in the art would recognize that many methods may be used forrescaling images without departing from the spirit or the scope of theinvention.

Resized image display window 504 corresponds to a displayable area on aclient device when a user wishes to view the image data at a greaterresolution than the resolution of tiles 500. Reference window 504 isshown to illustrate the size of an image display window that is usedwhen a user views the image data at an exact resolution of theresolution of tiles 500. A displayable image is generated from areas518-528 of overlap images 506-516. Overlap images 506-516 comprise asubset of tiles 500 that overlap with resized image display window 504.The displayable image may be constructed by either a server of the imagedata management system or the client device. In one or more embodiments,the displayable image is constructed by a GPU of the client device byindividually processing overlapping images 506-516, where overlap images506-516 are limited in size based on a GPU limitation. The GPUlimitation may include a memory limitation, an image size limitation, orany other GPU limitation, including limitations imposed on GPUprocessing that are external to the GPU. For example, the GPU may beconfigured to process overlap images 412-422 in series, updating atleast a portion of the displayable image with at least a portion of eachoverlap image as it is processed.

Resized image display window 530 corresponds to a displayable area on aclient device when a user wishes to view the image data at a lowerresolution than the resolution of tiles 500. Reference window 532 isshown to illustrate the size of an image display window that is usedwhen a user views the image data at an exact resolution of theresolution of tiles 500. A displayable image is generated from areas548-558 of overlap images 534-546. Overlap images 534-546 comprise asubset of tiles 500 that overlap with resized image display window 530.The displayable image may be constructed by either a server of the imagedata management system or the client device. In one or more embodiments,the displayable image is constructed by a GPU of the client device byindividually processing overlapping images 534-546, where overlap images534-546 are limited in size based on a GPU limitation. The GPUlimitation may include a memory limitation, an image size limitation, orany other GPU limitation, including limitations imposed on GPUprocessing that are external to the GPU. For example, the GPU may beconfigured to process overlap images 534-546 in series, updating atleast a portion of the displayable image with at least a portion of eachoverlap image as it is processed.

FIG. 6 illustrates an exemplary use of windowing in accordance with oneor more embodiments of systems and methods for image data management.

In one or more embodiments, GPU limitations may affect an imagedimension as well as other image constraints. For example, in one ormore embodiments, a bit depth of an image may be modified to accommodateone or more GPU limitations.

In one or more embodiments, providing a user high-resolution image datainvolves retaining bit depth information present in the originalhigh-resolution image data, including medical imaging data such as datathat complies with the DICOM file format definition. In one or moreembodiments, the tiled representation comprises full-resolution tilesand reduced-resolution tiles include tiles at the original bit depth ofthe high-resolution image data. One of ordinary skill in the art wouldappreciate that many methods may be used to reduce a bit depth toaccommodate a GPU limitation without losing the higher bit depthinformation. An exemplary windowing procedure is shown in FIG. 6 forillustrative purposes.

Histogram 600 corresponds to bit depth information 602 for an exemplaryimage. Histogram 600 has x-axis 610 and y-axis 612. X-axis 610corresponds to a bit depth of the exemplary image. The bit depth is anybit depth suitable for any high-resolution image data. For example, atypical bit depth of 16 may be used, leading to an x-axis 610 range of[0, 65536], [−32768, 32767], or any other range equivalent to a bitdepth of 16.

If a lower bit depth is desirable based on the GPU limitation, awindowing technique may be used to modify the exemplary image before GPUprocessing. Based on one or more user selections, window 606 isdetermined. The bit depth information 602 within window 606 is used togenerate a modified image with the lower bit depth. The pixel values maybe normalized, such as to a range of between 0 and 1. The modified imagecontains all of the bit depth information within window 606. Themodified image is processed by the GPU to construct or modify adisplayable image on the client device.

In one or more embodiments, window 606 is determined based on a medianvalue 604 and a radius value 608. The median value 604 and a radiusvalue 608 may be modified based on one or more selections of a userviewing the high-resolution image data.

In one or more embodiments, the server transmits an exemplary image withthe original bit depth to the client device, and the client devicemodifies the exemplary image before GPU processing. The client devicemay save the exemplary image with the original bit depth such that thewindowing process may be repeated by the client device when a userchanges windows 606.

FIG. 7 is a flowchart for an exemplary method for processing image datain accordance with one or more embodiments of systems and methods forimage data management. Process 700 begins at step 702.

Processing continues to step 704, where a high-resolution data set isobtained. The dataset includes high-resolution image data. The imagedata may include video data. In one or more embodiments, the data setincludes full resolution medical imaging data. The medical imaging datamay include any medical imaging data that complies with the DICOM fileformat definition.

Processing continues to step 706, where scaled image data is generated.A plurality of scaled full images is generated, where each scaled fullimage is a full representation of the image data. The scaled full imagesinclude a full resolution image and at least one reduced resolutionimage. The scaled full images may include a lowest resolution image witha size limitation based on a GPU limitation. The plurality of reducedresolutions may be reduced by a factor of m (e.g. 1/m, 1/(m²), . . .1/m^(n), where n is an integer greater than or equal to 1 and where m isa real number greater than 1). In one or more embodiments, the pluralityof reduced resolutions is reduced by 2 in each dimension (e.g. ½, ¼, . .. ½^(n), where n is an integer greater than or equal to 1).

Processing continues to step 708, where a plurality of full-resolutiontiles is generated based on the full resolution image. In one or moreembodiments, none of the high-resolution tiles are larger than themaximum tile size. The maximum tile size may be based on an image sizeor a file size. In one or more embodiments, the maximum tile size isbased on a GPU limitation, including a memory limitation, an image sizelimitation, or any other GPU limitation, including limitations imposedon GPU processing that are external to the GPU. In one or moreembodiments, the maximum tile size for a 2D image is 1024×1024.Alternatively, a maximum tile size for a 2D image may be set at2048×2048, or any other limit based on a GPU limitation. The maximumfile size may also be set by a memory size. For example, in one or moreembodiments, the maximum file size is about 5 MB. Alternatively, thetile may exceed a GPU limitation when a tile is at a current bit depth,but may meet a GPU limitation when the bit depth is reduced.

Processing continues to step 710, where a plurality ofreduced-resolution tiles are generated based on the at least one reducedresolution image. Processing continues to step 708, where a plurality offull-resolution tiles is generated. In one or more embodiments, none ofthe high-resolution tiles are larger than the maximum tile size. Themaximum tile size may be based on an image size or a file size. In oneor more embodiments, the maximum tile size is based on a GPU limitation,including a memory limitation, an image size limitation, or any otherGPU limitation, including limitations imposed on GPU processing that areexternal to the GPU. In one or more embodiments, the maximum tile sizefor a 2D image is 1024×1024. Alternatively, a maximum tile size for a 2Dimage may be set at 2048×2048, or any other limit based on a GPUlimitation. Alternatively, the tile may exceed a GPU limitation when atile is at a current bit depth, but may meet a GPU limitation when thebit depth is reduced.

Processing continues to step 712, where a representation of the data setis stored. The tiled representation of the data set includes theplurality of scaled full images at a plurality of resolutions, theplurality of high-resolution tiles, and the plurality of reducedresolution tiles.

The data set may include metadata associated with the image. Themetadata may be associated with specific pixels, areas or other featuresof the high-resolution image data. In one or more embodiments, the tiledrepresentation includes metadata associated with the image. The metadatamay be associated with high-resolution tiles, reduced resolution tiles,and/or scaled full images that contain features of the high-resolutionimage data associated with the metadata. In one or more embodiments, anymetadata specified in the DICOM standard may be associated withhigh-resolution tiles, reduced resolution tiles, and/or scaled fullimages.

Processing continues to step 714 where process 700 terminates.

FIG. 8 is a flowchart for an exemplary method for providing image datain accordance with one or more embodiments of systems and methods forimage data management. Process 800 begins at step 802.

Processing continues to step 804, where a request to access a tiledrepresentation of a data set is received from a client device. The tiledrepresentation includes a plurality of high-resolution tiles and aplurality of reduced resolution tiles of high-resolution image data. Theplurality of reduced resolutions may reduced by a factor of m (e.g. 1/m,1/(m²), . . . 1/m^(n), where n is an integer or equal to 1 and where mis a real number greater than 1). The plurality of reduced resolutionstiles may include tiles at least one reduced resolution. In one or moreembodiments, the reduced resolutions are ¼, . . . ½^(n), where n is aninteger or equal to 1. None of the high-resolution tiles and reducedresolution tiles is larger than the maximum tile size. The maximum tilesize may be based on an image size or a file size. In one or moreembodiments, the maximum tile size is based on a GPU limitation. In oneor more embodiments, the data set includes full resolution medicalimaging data, such as data that complies with the Digital Imaging andCommunications in Medicine (DICOM) file format definition.

Processing continues to step 806, where an image display window isdetermined. The image display window is used to determine theappropriate portion of the data set to provide the client device. Theimage display window corresponds to a viewable area to be displayed on adisplay device of a client device. The image display window may bedetermined based on position and dimension information obtained from theclient device. The image display window may correspond to a desiredresolution, which may be obtained as additional data, or may becalculated based on the image display window.

Processing continues to step 808, where the tiled representation of thedata set is accessed. Depending on the desired resolution, the tilesaccessed may be from the high-resolution tiles or the reduced resolutiontiles of a desired resolution.

Processing continues to step 810, where at least one overlapping imageis determined. The at least one overlapping image include tiles of thedesired resolution that overlap with the image display window.

Processing continues to step 812, where at least a portion of the atleast one overlapping image is sent to the computing device. The entireoverlapping image may be sent to the computing device. Alternatively,only the overlapping portion of the overlapping image is sent. In one ormore embodiments, the computing device has access to one or moreoverlapping images from a previous operation or from background datatransfer. In this case, one or more overlapping images may not be sent.

Processing continues to optional step 814, where metadata associatedwith the dataset is provided to the computing device. The metadata mayinclude data that complies with the DICOM file format definition. In oneor more embodiments, the metadata provided to the computing devicecorresponds to metadata that is relevant to a portion of thehigh-resolution image data that corresponds to the image display window.

Processing continues to optional step 816, where background data issent. The background data includes the high-resolution tiles and thereduced resolution tiles. The background data may also include metadataassociated with the high-resolution image data. In one or moreembodiments, background data is sent to the computing device when noother data requests are pending, such as requests based on an imagedisplay window. The transmittal of background data may be sent in aprioritized order. For example, a formula may be used to calculate aweight based on the likelihood that the computing device will requestthe data. The weight may be based on a distance function that takes intoaccount a current image display window position and a current imagedisplay window resolution.

Processing continues to step 818, where process 800 terminates.

FIG. 9 is a flowchart for an exemplary method for providing image datain accordance with one or more embodiments of systems and methods forimage data management. Process 900 begins at step 902.

Processing continues to step 904, where a request to access data isreceived. The request received is a request to access data correspondingto an updated image display window. An image display window may beupdated based on input by a user of the computing device. For example, auser may attempt to change a position and/or resolution of the imagedisplayed on the computing device.

Processing continues at step 906, where updated images to send aredetermined. The updated images are determined based on the updated imagedisplay window such as a position and/or resolution corresponding to theupdated image display window. The updated images may include tiles ofthe desired resolution that overlap with the updated image displaywindow.

Processing continues to step 908, where the updated images are sent tothe device for display. For any updated image, the entire updated imagemay be sent to the computing device. Alternatively, only the overlappingportion of the updated image is sent. In one or more embodiments, thecomputing device has access to one or more of the updated images from aprevious operation or from background data transfer. In this case, oneor more updated images may not be sent.

Processing continues to optional step 910, where metadata associatedwith the dataset is received from the computing device. The metadata mayinclude data that complies with the DICOM file format definition. In oneor more embodiments, the metadata provided to the computing devicecorresponds to metadata that is relevant to a portion of thehigh-resolution image data that corresponds to the image display window.The metadata may be added by the user of the computing device. Themetadata includes analysis, diagnosis and/or treatment information madeby a medical professional, such as a user of the computing device.

Processing continues to optional step 912, where the new metadata isassociated with the dataset.

Processing continues to step 914, where process 900 terminates.

FIG. 10 is a flowchart for an exemplary method for displaying image datain accordance with one or more embodiments of systems and methods forimage data management. Process 1000 begins at step 1002.

Processing continues to step 1004, where a request to access imagingdata from a server is sent. The imaging data may include high-resolutionimage data and/or video data.

Processing continues to step 1006, where an initial image is received.The initial image may be a scaled full image of the high-resolutionimage data. In one or more embodiments, the initial image is limited insize based on a GPU limitation.

Processing continues to step 1008, where the initial image is processedon a GPU to generate a displayed image. In one or more embodiments, theinitial image is processed to reduce a bit depth of the initial imagebefore processing the initial image on the GPU.

Processing continues to step 1010, where the displayed image isdisplayed on a display device. The displayed image includes at least aportion of the initial image.

Processing continues to step 1012, where a plurality of overlap imagesare received from the server. A resolution of the overlap images ishigher than the resolution of the initial image received. The overlapimages may correspond to an image display window.

Processing continues to step 1014, where the plurality of overlap imagesare processed on the GPU to update the displayed image. In one or moreembodiments, the plurality of overlap images is processed to reduce abit depth of the overlap images before processing the overlap images onthe GPU. The bit depth may be selectively reduced to retain a specificsubset of information present in the overlap images. The plurality ofoverlap images may be processed in series on the GPU based on thelimitations of the GPU. When the GPU processes an overlap image, it mayuse at least a portion of the overlap image to update at least a portionof the displayed image. Upscaling and/or downscaling operations may beperformed to update the displayed images.

Processing continues to optional step 1016, where metadata associatedwith the displayed image is received. In one or more embodiments, themetadata associated with the displayed image includes metadataassociated with the overlap images and/or a portion of thehigh-resolution image data that corresponds to the image display window.

Processing continues to optional step 1018, where the metadata isdisplayed on the display device.

Processing continues to optional step 1020, where background data isreceived. In one or more embodiments, the background data includesunsent image data selected from a plurality of high-resolution tiles andthe plurality of reduced resolution tiles that make up the tiledrepresentation of a dataset. Background data may be streamed when noactive request for other data from the server is pending. The backgrounddata may be prioritized based on one or more factors, such as anymeasure of distance from the current image display window.

Processing continues to step 1022, where process 1000 terminates.

FIG. 11 is a flowchart for an exemplary method for displaying medicalimaging data in accordance with one or more embodiments of systems andmethods for image data management. Process 1100 begins at step 1102.

Processing continues to step 1104, where a request to access medicalimaging data from a server is sent. The medical imaging data may complywith the Digital Imaging and Communications in Medicine (DICOM) fileformat definition.

Processing continues to step 1106, where an initial image is received.The initial image may be a scaled full image of the medical image data.In one or more embodiments, the initial image is limited in size basedon a GPU limitation.

Processing continues to step 1108, where the initial image is processedon a GPU to generate a displayed image. In one or more embodiments, theinitial image is processed to reduce a bit depth of the initial imagebefore processing the initial image on the GPU.

Processing continues to step 1110, where the displayed image isdisplayed on a display device. The displayed image includes at least aportion of the initial image.

Processing continues to step 1112, where a plurality of overlap imagesare received from the server. A resolution of the overlap images ishigher than the resolution of the initial image received. The overlapimages may correspond to an image display window.

Processing continues to step 1114, where the plurality of overlap imagesare processed on the GPU to update the displayed image. In one or moreembodiments, the plurality of overlap images is processed to reduce abit depth of the overlap images before processing the overlap images onthe GPU. The bit depth may be selectively reduced to retain a specificsubset of information present in the overlap images. In one or moreembodiments, the plurality of overlap images is processed in series onthe GPU based on the limitations of the GPU. When the GPU processes anoverlap image, it may use at least a portion of the overlap image toupdate at least a portion of the displayed image. Upscaling and/ordownscaling operations may be performed to update the displayed images.

Processing continues to optional step 1116, where metadata associatedwith the displayed image is received. The metadata may include data thatcomplies with the DICOM file format definition. In one or moreembodiments, the metadata includes analysis, diagnosis and/or treatmentinformation made by a medical professional.

Processing continues to optional step 1118, where the metadata isdisplayed on the display device.

Processing continues to optional step 1120, where background data isreceived. In one or more embodiments, the background data includesunsent image data selected from a plurality of high-resolution tiles andthe plurality of reduced resolution tiles that make up the tiledrepresentation of a dataset. Background data may be streamed when noactive request for other data from the server is pending. The backgrounddata may be prioritized based on one or more factors, such as anymeasure of distance from the current image display window.

Processing continues to step 1122, where process 1100 terminates.

FIG. 12 is a flowchart for an exemplary method for image datacollaboration in accordance with one or more embodiments of systems andmethods for image data management. Process 1200 begins at step 1202.

Processing continues to step 1204, where a change in view from the useris accepted. A change in the view from the user may include a change inposition and/or a change in resolution.

Processing continues to decision step 1206, where it is determinedwhether more images are required. In one or more embodiments, moreimages may be required when an image display window changes, such aswhen a user navigates image data.

When more images are still required, processing continues to decisionstep 1208, where it is determined whether the images are availablelocally. An image may be available locally if it was stored after it isinitially received in response to a request. An image may also beavailable locally if it was received as background data.

If images are available locally, processing continues to step 1214. Ifimages are available not available locally, processing continues to step1210, where a request is sent to a server for more image data. In one ormore embodiments, the images required are determined locally. Suchimages may be defined based on at least one of position information andresolution information. Alternatively, the images required may bedetermined by the server.

Processing continues to step 1212, where the next requested image isreceived from the server. In one or more embodiments, all imagesrequired are requested in one step, and processing continues based onthe availability of each image.

Processing continues to step 1214, where the next image is processed onthe GPU to update at least a portion of the displayed image. In one ormore embodiments, the plurality of overlap images is processed in serieson the GPU based on the limitations of the GPU. When the GPU processesan overlap image, it may use at least a portion of the overlap image toupdate at least a portion of the displayed image. Upscaling and/ordownscaling operations may be performed to update the displayed images.

Processing continues to decision step 1206.

Returning to decision step 1206, if no more images are required,processing continues to step 1216, where process 1200 terminates.

FIG. 13 illustrates an exemplary collaborative image data managementsystem in accordance with one or more embodiments of systems and methodsfor image data management. System 1300 includes image data managementsystem 1302 and client devices 1310-1316.

Image data management system 1302 includes collaboration module 1308.

Collaboration module 1308 is configured to manage one or morecollaboration sessions between a plurality of client devices. In theexample shown, collaboration module 1308 is managing a collaborationsession between client devices 1310-1316.

Each client device 1310-1316 is connected to collaboration module 1308over network connections 1320-1326. In one or more embodiments, networkconnections 1320-1326 are lightweight network connections capable ofhandling low bandwidth image navigation information. The imagenavigation information is generated by controlling client device 1312.Controlling client device 1312 possesses session navigation control key1328. In one or more embodiments, any of client devices 1310-1316 mayrequest session navigation control key 1328. Alternatively, sessionnavigation control may be restricted to specific client devices. In oneor more embodiments, network connections 1320-1326 are further capableof handling communication, including voice and text communicationbetween client devices 1310-1316. In a higher-bandwidth application,network connections 1320-1326 may be enabled to handle videocommunication between client devices 1310-1316. Communication may bedirected to all client devices in a collaboration session or any subsetthereof. In the case that network connection 1322 of controlling clientdevice 1312 is interrupted, session navigation control key 1328 may bepassed to another client device 1310-1316.

Image data management system 1302 further includes image data store 1304and data streaming module 1306. Data streaming module 1306 is configuredto deliver at least a portion of a tiled representation stored in imagedata store 1304 and to client devices 1310-1316. The data provided bydata streaming module 1306 is delivered over network connections1330-1336. Each client device 1310-1316 maintains an independent networkconnection 1330-1336 to request and receive image data.

Client devices 1310-1316 are configured to request data from datastreaming module 1306 based on image navigation data received fromcollaboration module 1308. Controlling client device 1312 may requestdata from data streaming module 1306 either based on navigation datagenerated by its user, or navigation data received from collaborationmodule 1308 to ensure synchronization of navigation between controllingclient device 1312 and other client devices in the collaborationsession.

Network connections 1320-1326 and 1330-1336 may include connections overone or more networks, including one or more Local Area Networks (LAN),Wide Area Networks (WAN), wireless networks, cellular data networks,optical networks, distributed networks, the Internet, or any combinationthereof.

While the invention herein disclosed has been described by means ofspecific embodiments and applications thereof, numerous modificationsand variations could be made thereto by those skilled in the art withoutdeparting from the scope of the invention set forth in the claims.

What is claimed is:
 1. A method of accessing high resolution image datacomprising: accessing a tiled representation of an image data athigh-resolution, said tiled representation comprising a plurality ofhigh-resolution tiles and a plurality of reduced-resolution tiles;receiving a request to access said image data from a computing device,wherein said computing device is communicatively coupled with a displaydevice; determining an image display window based on said request fromsaid computing device, wherein said image display window corresponds toa displayable area on said display device; determining at least oneoverlap image to send said computing device based on said image displaywindow, wherein said at least one overlap image is selected from saidplurality of high-resolution tiles and said plurality of reducedresolution tiles; and sending at least a portion of said at least oneoverlap image to said computing device for display in real time.
 2. Themethod of claim 1, wherein each of said plurality of high resolutiontiles is based on a maximum tile size that is dependent on a GPU limit.3. The method of claim 2, wherein said maximum tile size is 1024 pixelsby 1024 pixels.
 4. The method of claim 1, wherein said image datacomprises a plurality of pixels at 16 bits per pixel.
 5. The method ofclaim 1, wherein said plurality of reduced resolution tiles compriseresolutions of ½^(n) in each dimension compared to said high resolutiontiles, where n is an integer greater than or equal to
 1. 6. The methodof claim 1, wherein said at least one overlap image comprises aplurality of tiles at a new resolution, wherein said new resolution isthe next higher resolution generated compared to a resolution currentlydisplayed on said display device.
 7. The method of claim 1, furthercomprising: receiving a request from said computing device to accessdata corresponding to an updated image display window; determining atleast one updated image to send said computing device based on saidupdated image display window, wherein said at least one updated image isselected from said plurality of high-resolution tiles and said pluralityof reduced resolution tiles; and sending said at least one updated imageto said computing device for display in real time.
 8. The method ofclaim 1, wherein said image data comprises full-resolution medicalimaging data.
 9. The method of claim 1, further comprising providingmetadata associated with said image data to said computing device.
 10. Amethod of accessing high resolution image data comprising: obtaining ahigh-resolution image data; generating a plurality of scaled full imagesfrom said high resolution image data at a plurality of resolutionscomprising a full resolution image and at least one reduced resolutionimage; generating a plurality of high-resolution tiles based on saidfull resolution image; generating a plurality of reduced-resolutiontiles based on said at least one reduced resolution image; and receivinga request to access said image data from a computing device, whereinsaid computing device is communicatively coupled with a display device;determining an image display window based on said request from saidcomputing device, wherein said image display window corresponds to adisplayable area on said display device; determining at least oneoverlap image to send said computing device based on said image displaywindow, wherein said at least one overlap image is selected from saidplurality of high-resolution tiles and said plurality of reducedresolution tiles; and sending at least a portion of said at least oneoverlap image to said computing device for display in real time.
 11. Themethod of claim 10, wherein each of said plurality of high resolutiontiles is based on a maximum tile size that is dependent on a GPU limit.12. The method of claim 10, wherein said image data comprises aplurality of pixels at 16 bits per pixel.
 13. The method of claim 10,wherein said plurality of reduced resolution tiles comprise resolutionsof ½^(n) in each dimension of said high resolution tiles, where n is aninteger greater than or equal to
 1. 14. The method of claim 10, whereinsaid image data comprises full-resolution medical imaging data.
 15. Themethod of claim 14, wherein said medical imaging data complies with theDigital Imaging and Communications in Medicine (DICOM) file formatdefinition.
 16. A system for managing high resolution image datacomprising: a server with high resolution image data; a computing devicecommunicatively coupled to said server, wherein said computing device isconfigured with a display device and a graphical processor unit (GPU),wherein said computing device is further configured to: send a requestto said server for a view said image data; receive an initial image fromsaid server based on image display window of said display device,wherein said server determines said image display window from saidrequest; display said initial image on said display device; receive aplurality of overlap images from said server, wherein a resolution ofsaid plurality of overlap images is higher than a resolution of saidinitial image, and wherein said plurality of overlap images is limitedin size; process said plurality of overlap images on said GPU to updateat least a portion of said displayed image with at least a portion ofsaid plurality of overlap images.
 17. The system of claim 15, whereinsaid plurality of overlap images is limited in size based on limitationof said GPU.
 18. The system of claim 15, wherein said image datacomprises a plurality of pixels at 16 bits per pixel.
 19. The system ofclaim 15, wherein said image data comprises full-resolution medicalimaging data.
 20. The system of claim 19, wherein said medical imagingdata complies with the Digital Imaging and Communications in Medicine(DICOM) file format definition.